TURN Server single node deployment:

Scenario1:

TURN Server is deployed into DMZ, other media components deployed in internal network and do not have any direct connectivity with TURN Server.

Port/Port Range	Transport	From	To
3478	UDP/TCP	Internal Client, External Client	TURN Server
49152-65535	UDP	Internal Client	TURN Server
20830-20930	UDP	TURN Server	Internal Client
49152-65535	UDP	VMCU	TURN Server
40000-49999	UDP	TURN Server	VMCU
40000-49999	UDP	Internal Client	VMCU
20830-20930	UDP	VMCU	Internal Client

General Configuration:

TURN server machine has one interface -
No changes required into TurnServer.properties file.

TURN server machine has multiple interface ( Private and Public ) -
turn.local.hostname.ipv4=
turn.allocation.hostname.ipv4=
Note: If internal clients are in same subnet then it is not necessary that clients connect to TURN server. To achieve this configure the TURN server DNS split horizon so that internal client will resolve TURN hostname to 0.0.0.0 and external client will resolve TURN hostname to public IP.

Scenario2:

TURN Server is deployed into DMZ, other media components also deployed in DMZ network and do have direct connectivity with TURN Server.

Ports Configuration:

Port/Port Range	Transport	From	To
3478	UDP/TCP	Internal Client, External Client	Internal Client
49152-65535	UDP	Internal Client	TURN Server
20830-20930	UDP	TURN Server	Internal Client
49152-65535	UDP	VMCU	TURN Server
40000-49999	UDP	TURN Server	VMCU
40000-49999	UDP	Internal Client	VMCU
20830-20930	UDP	VMCU	Internal Client

General Configuration

TURN server machine has one interface
No changes required into TurnServer.properties file.
TURN server machine has multiple interface ( Private and Public )
turn.local.hostname.ipv4=
turn.allocation.hostname.ipv4=
Note: If internal clients are in same subnet then it is not necessary that clients connect to TURN server. To achieve this configure the TURN server DNS split horizon so that internal client will resolve TURN hostname to 0.0.0.0 and external client will resolve TURN hostname to public IP.


TURN Server cluster deployment:

1. TURN Server cluster deployment using IBM Load-Balancer

http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/install/inst_config_turn_loadbalance.dita?lang=en


2. TURN Server cluster deployment using Big IP F5 Load-Balancer
Case 1: TURN Server Fronted by F5 Load-Balancer

-- TURN Server should have internal IP address assigned. Configure below properties in TurnServer.properties file -
turn.local.hostname.ipv4= turn.allocation.hostname.ipv4=
-- Create two Virtual hosts on Big IP (F5) for UDP-3478 and TCP-3478

-- Virtual hosts should have pool defined which has all TURN server nodes added as pool member and those are connecting to TURN NIC internal interface.

-- Same client connection should go to same TURN server member and requires persistence rule tobe applied on TURN Server virtual Host.

- Login to F5 admin console
- Navigate to : Local Traffic --> Virtual Servers --> Virtual Server List
- Search for TURN Server virtual host and click the link.
- Goto 'Resources' section
- In Default Persistence Profile, select 'source_addr'
- Click 'Update'.

-- F5 Virtual Host allocated for TURN Server must have Public IP assigned and accessible from client machine.

Port Configuration:

Port/ Port Range	Transport	From	To
3478	UDP/TCP	Internal Client, External Client	TURN Server F5 VH
49152-65535	UDP	Internal Client	TURN Server Internal IP
20830-20930	UDP	TURN Server Internal IP	Internal Client
49152-65535	UDP	VMCU	TURN Server Internal IP
40000-49999	UDP	TURN Server Internal IP	VMCU
40000-49999	UDP	Internal Client	VMCU
20830-20930	UDP	VMCU	Internal Client

Case 2: External (Public) address available for TURN Server nodes

-- TURN Server should have two network interface card (NIC-Public and NIC-Internal). Configure below properties in TurnServer.properties file -

turn.local.hostname.ipv4= turn.allocation.hostname.ipv4= turn.loopback.hostname.ipv4= turn.redirect.hostname.ipv4=
-- Create two Virtual hosts on Big IP (F5) for UDP-3478 and TCP-3478

-- Virtual host (VH1) should have pool defined which has all TURN server nodes added as pool member and those are connecting to TURN NIC internal interface.

-- Virtual Host and all TURN Server nodes should have Public IP assigned and accessible from client machine.

Port Configuration:

Port/Port Range	Transport	From	To
3478	UDP / TCP	Internal Client, External Client	TURN Server nodes and TURN F5 VH
49152-65535	UDP	Internal Client	TURN Server Internal IP
20830-20930	UDP	TURN Server Internal IP	Internal Client
49152-65535	UDP	VMCU	TURN Server Internal IP
40000-49999	UDP	TURN Server Internal IP	VMCU
40000-49999	UDP	Internal Client	VMCU
20830-20930	UDP	VMCU	Internal Client

Case 3: External address not available for TURN Server

-- TURN Server should have two network interface card (NIC-1 and NIC-2). Configure below properties in TurnServer.properties file -
turn.local.hostname.ipv4= turn.allocation.hostname.ipv4= turn.loopback.hostname.ipv4= turn.redirect.hostname.ipv4=
-- Create N+1 Virtual hosts on Big IP F5 ('N' represents number of TURN Server nodes)

-- One Virtual host (VH1) should have pool defined which has all TURN server nodes added as pool member and those are connecting to TURN NIC-2.

-- Other virtual hosts have pool assigned where those pools have one to one mapping with TURN Server node and those pool members are connecting TURN servers NIC-1.

-- All N+1 Virtual Hosts should have Public IP assigned and accessible from client machine.
Port Configuration:

Port/Port Range	Transport	From	To
3478	UDP/TCP	Internal Client, External Client	All N+1 TURN Server F5 VH
49152-65535	UDP	Internal Client	TURN Server Internal IP
20830-20930	UDP	TURN Server Internal IP	Internal Client
49152-65535	UDP	VMCU	TURN Server Internal IP
40000-49999	UDP	TURN Server Internal IP	VMCU
40000-49999	UDP	Internal Client	VMCU
20830-20930	UDP	VMCU	Internal Client